I guess eventually it could be better handle this completely inside the mini parser regarding parsing the types of chords and outputting stacks as a result etc.

With regard to the current implementation, the good quirk of the Name way of doing this was that you could append chord info to multiple events at once like <[c c c] [d d] a>:min. Maybe ' should be an operator expression like : to allow for this kind of use?

<[c c c] [d d] a>:min

This would have been parsed as Pitch + Target - and still is? So using Name instead of the new Chord doesn't change anything here.

As long as we're not breaking basic tidal compatibility, either way is fine for me.

But yes, using ' as a new operator would indeed be the cleanest solution, but I'm not really keen to duplicate all the chord parsing functionality in the cycle. You'd also have to extend the parser to handle all kinds of supported chords, which seems awkward.

Apropos: I'm not a fan of the tidal `ii chord inversion notation. I find it quite confusing and limiting, but that probably should be supported sometime in the future as well...

@unlessgames to merge or not to merge.

If you dislike the chord changes in the grammar, I'm fine with that and will parse that from the name. I don't think it's causing any harm and can later still be finetuned.

Sorry, I don't dislike the changes, was just still wondering if somehow extending the Target system to include chords was a better start, but probably not. This already works so let's merge.